home *** CD-ROM | disk | FTP | other *** search
-
-
-
- mmmmtttt((((1111)))) mmmmtttt((((1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- mt - magnetic tape manipulating program
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- mmmmtttt [ ----ffff ttttaaaappppeeeennnnaaaammmmeeee ] command [ count ]
- mmmmtttt [ ----tttt ttttaaaappppeeeennnnaaaammmmeeee ] command [ count ]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- _m_t is used to give commands to the magnetic tape drives. By default, _m_t
- performs the requested operation using /_d_e_v/_n_r_t_a_p_e. Normally the
- operations are performed once. Some operations may be performed multiple
- times by specifying _c_o_u_n_t . For all others, _c_o_u_n_t is ignored. _c_o_u_n_t is
- parsed with the _s_t_r_t_o_l(3) library routine, which means that values with
- leading 0's are taken as octal, those with leading 0x or 0x are taken to
- be hex, and other's are taken to be decimal.
-
- To use an alternate device, one of the options ----ffff ttttaaaappppeeeennnnaaaammmmeeee or ----tttt ttttaaaappppeeeennnnaaaammmmeeee
- may be specified. If one of these options is not used, then _m_t will
- check for an environment variable TTTTAAAAPPPPEEEE and use that, if set. Otherwise
- the default device, /_d_e_v/_n_r_t_a_p_e is used.
-
- The ttttaaaappppeeeennnnaaaammmmeeee field can also reference a remote tape device. A remote
- tape device name has the form:
-
- [_u_s_e_r@]system:/dev/???
-
- Where _s_y_s_t_e_m is the remote system, /_d_e_v/??? is the particular drive on
- the remote system (raw, rewinding, non-rewinding, etc.), and the optional
- _u_s_e_r is the login name to be used on the remote system (the default is
- the current login name). The interface requires that the device portion
- of the name start with /_d_e_v in order to be considered as a potential
- remote device.
-
- Note that when using a remote tape device, many commands may not be
- supported by machines not running IRIX, and the meaning of some of the
- status and position bits for the ssssttttaaaattttuuuussss command may differ.
-
- If the rewind device is used, some commands are (long) null operations.
- In particular, the ffffeeeeoooommmm and ffffssssffff commands will result in the tape being
- positioned at BOT when the rewind device is used, rather than the
- requested position.
-
- The available commands are listed below. Only as many characters as are
- required to uniquely identify a command need be specified. Note that not
- all commands are implemented for all devices. For most of the commands
- that accept a count, the default is 1, if not specified. Not all
- commands are implemented by all devices or device drivers. Some may
- return an error, others may return with no error, but not do anything
- (such as attempting to retension a tape on a DAT drive).
-
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- mmmmtttt((((1111)))) mmmmtttt((((1111))))
-
-
-
- For those cases where the description seems unclear, it may be helpful to
- refer to the comments in ////uuuussssrrrr////iiiinnnncccclllluuuuddddeeee////ssssyyyyssss////mmmmttttiiiioooo....hhhh.
-
- _m_t returns a 0 exit status when the operation was successful, a 1 if a
- command was unrecognized, and a 2 if a operation failed. _m_t without any
- arguments defaults to hhhheeeellllpppp.
-
-
- wwwweeeeooooffff Write _c_o_u_n_t end-of-file marks at the current position on the tape.
-
- wwwwsssseeeettttmmmmkkkk
- Write _c_o_u_n_t setmarks at the current position on the tape; currently
- only supported for DAT, setmarks are intended for grouping tape
- files into sets.
-
- ffffssssffff Forward space _c_o_u_n_t tape files. The resulting position is on the
- EOT side of the filemark.
-
- ffffssssrrrr Forward space _c_o_u_n_t records (blocks).
-
- bbbbssssffff Backspace _c_o_u_n_t tape files. The resulting position is on the BOT
- side of the filemark.
-
- bbbbssssrrrr Backspace _c_o_u_n_t records (blocks).
-
- ssssppppsssseeeettttmmmmkkkk
- space _c_o_u_n_t setmarks. The count is negative to space towards BOT,
- and positive to space towards EOT.
-
- rrrreeeewwwwiiiinnnndddd
- Rewind the tape to BOT, or in the case of partitioned tapes, to the
- beginning of the current partition (it does NOT change partitions).
-
- ssssppppppppaaaarrrrtttt
- Space to the given partition. Currently only supported for DAT
- tape. The resulting position is the beginning of the partition, if
- it exists. Only partitions 0 and 1 are supported for DDS format DAT
- tapes. Partition 1 is the one closest to BOT. Once within a
- partition, all other commands (except sppart or mkpart) apply to
- that partition only, including rewind, erase, and feom.
-
- mmmmkkkkppppaaaarrrrtttt
- Create a partitioned tape. Currently only supported for DAT tape.
- The argument specifies the size in megabytes of the partition
- closest to BOT, which is known as partition 1. That part of the
- tape is written and checked for errors. This is intended primarily
- so that tape directories may be written at the beginning of the tape
- with no possibility of overwriting the primary data on the tape. An
- argument of 0 creates a single partition tape again.
-
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-
-
-
- mmmmtttt((((1111)))) mmmmtttt((((1111))))
-
-
-
- ffffeeeeoooommmm Forward space to end of recorded data. This allows appending new
- tape files to a tape that already contains data. For partitioned
- tapes, positions to the end of recorded data in the current
- partition.
-
- oooofffffffflllliiiinnnneeee
- Rewind and unload the tape from the drives heads, allowing removal
- of the tape. The tape is not ejected for most drive types.
- Use the uuuunnnnllllooooaaaadddd option to force ejection (for drives that support
- ejection or similar behavior; not all drives do).
-
- uuuunnnnllllooooaaaadddd
- Inform the drive it is OK for the tape to be removed. This is
- meaningful only for drives such as the 8mm drive that enable and
- disable the eject button under software control. Some drives will
- otherwise not allow tape removal if the tape has not been previously
- rewound. If the drive supports it, the tape is ejected.
-
- eeeerrrraaaasssseeee
- Erase from current position to EOT. This can be very slow for some
- tape drives (up to 2 hours for 8mm tape drives with 2.3Gb capacity).
- Note that for QIC drives, aaaallllllll tracks are erased simultaneously (QIC
- writes in serpentine fashion, with anywhere from 9-30 tracks,
- currently). This means that one should not expect to be able to
- erase just the "tail end" of a QIC tape, without losing most, if not
- all, of the data on the tape. The erase function is not supported
- on DAT drives when they are in audio mode. The erase function is
- not supported on Ampex DST drives.
-
- eeeexxxxiiiisssstttt
- Exit with status 0 if the drive exists, otherwise non-zero; this is
- primarily for use in scripts.
-
- rrrreeeecccceeeerrrrrrrroooonnnn
- Enable soft error reporting for drives that are very verbose about
- them, such as Cipher 540S; this persists until explicitly turned
- off. The default is rrrreeeecccceeeerrrrrrrrooooffffffff.
-
- rrrreeeecccceeeerrrrrrrrooooffffffff
- Disable soft error reporting for drives that are very verbose about
- them, such as Cipher 540S. This is the default behavior.
-
- ssssiiiilllliiii Suppress illegal length indicator (this occurs on tapes like the 8mm
- tape drive when a request is made to read fewer bytes than a block
- was written with, when in variable block mode). The default is to
- return a short count, when set, no short count will be returned, and
- the rest of the data in the block will be skipped. This is off by
- default. This persists until explicitly turned off or the tape is
- changed.
-
-
-
-
-
-
- PPPPaaaaggggeeee 3333
-
-
-
-
-
-
- mmmmtttt((((1111)))) mmmmtttt((((1111))))
-
-
-
- eeeeiiiilllliiii Reverses the effect of ssssiiiilllliiii (returns to default).
-
- aaaauuuuddddiiiioooo
- Set the tape device to be in audio mode if the argument is non-zero,
- or in data mode (the default) if it is zero. This is currently
- supported only for DAT tapes, and allows the transfer of digital
- audio music to and from the drive over the SCSI bus. In this mode,
- many of the data commands, such as weof are not allowed. The
- variable blocksize tape device should always be used when doing i/o
- in audio mode. The other tape parameters, such as recording
- frequency, program number, and so on must be transferred to the
- drive as part of the data stream. In addition, rewinds and seeks
- return immediately in audio mode, and further opens will block until
- they are complete. See the _t_p_s(7m) manual page for more
- information.
-
- sssseeeeeeeekkkk Seek to the block given as the argument. For multiple partition
- tapes, this is relative to start of partition, otherwise to BOT.
- When in audio mode, this specifies the program number (0 - 799)
- rather than a block number. The argument block number should be
- provided as a SCSI logical block number for SCSI tape drives, except
- for the STK drives, for which the argument is the block number in
- vendor unique format.
-
- ssssttttaaaattttuuuussss
- Print status information about the tape unit. It is not necessary
- to have media physically loaded to obtain status. The position
- information from the _m_t__d_p_o_s_n field of the structure returned by the
- MMMMTTTTIIIIOOOOCCCCGGGGEEEETTTT is printed for all drive types. For ttttppppssss (SCSI) drives,
- status information from the _m_t__e_r_r_e_g is also printed, which gives
- addition information about tape status. The current block position
- provided is the SCSI logical block address in all cases, except for
- the STK drives, which report the position in vendor unique block
- number format. The numeric field "Status" contains the mt_dposn
- bits in the low 16 bits, and the mt_erreg values in the upper 16
- bits. These bits are defined in /_u_s_r/_i_n_c_l_u_d_e/_s_y_s/_t_p_s_c._h.
-
- The meaning of the bits that are driver specific may vary from
- release to release, and are primarily useful when reporting tape
- problems to the customer support organization.
-
- bbbbllllkkkkssssiiiizzzzeeee
- Print the recommended block size for io, which is used by tar, cpio,
- bru, etc. A tape cartridge need not be physically loaded to obtain
- default block size, except that current block sizes will not be
- accurate in this case. The maximum, minimum, and current blocksizes
- are also reported; they may all be the same if the drive does not
- support variable block sizes.
-
- sssseeeettttbbbbllllkkkksssszzzz
- Sets the block size to be used when in fixed blocksize mode. Most
- drives that support variable sized blocks also support use of
-
-
-
- PPPPaaaaggggeeee 4444
-
-
-
-
-
-
- mmmmtttt((((1111)))) mmmmtttt((((1111))))
-
-
-
- different sized blocks in the fixed block mode. For example, this
- could be used to read 8 mm tapes written with a fixed block size of
- 512 bytes, rather than 1024, while still reading more than 512 bytes
- per system call. If this was not done, tape errors would occur.
- This size remains set until the next tape change, or until the drive
- is used in variable block mode.
-
- rrrreeeetttteeeennnnssssiiiioooonnnn
- Retension the tape in the drive. This may be a null operation on
- some drives, such as DAT.
-
- rrrreeeesssseeeerrrrvvvveeee
- Issues a request to reserve a tape device. This operation is
- persistent and remains until explicitly removed with a rrrreeeelllleeeeaaaasssseeee
- command. The SCSI tape interface (TPSC) uses the SCSI rrrreeeesssseeeerrrrvvvveeee
- command. Tape support (TS) uses the SCSI ppppeeeerrrrssssiiiisssstttteeeennnntttt rrrreeeesssseeeerrrrvvvveeee oooouuuutttt
- command if it is supported by the device; otherwise, the SCSI
- rrrreeeesssseeeerrrrvvvveeee command is used. This operation requires CCCCAAAAPPPP____DDDDEEEEVVVVIIIICCCCEEEE____MMMMGGGGTTTT
- capability.
-
- rrrreeeelllleeeeaaaasssseeee
- Issues a release request to a tape device. The SCSI tape interface
- (TPSC) uses the SCSI rrrreeeelllleeeeaaaasssseeee command. Tape support (TS) uses the
- SCSI ppppeeeerrrrssssiiiisssstttteeeennnntttt rrrreeeesssseeeerrrrvvvveeee oooouuuutttt command if it is supported by the
- device; otherwise, the SCSI rrrreeeelllleeeeaaaasssseeee command is used. This operation
- requires CCCCAAAAPPPP____DDDDEEEEVVVVIIIICCCCEEEE____MMMMGGGGTTTT capability.
-
- pppprrrreeeeeeeemmmmpppptttt
- Preempts reservations. This action should only be done in error
- recovery situations. Tape support (TS) uses the preempt service
- action of the SCSI ppppeeeerrrrssssiiiisssstttteeeennnntttt rrrreeeesssseeeerrrrvvvveeee oooouuuutttt command to preempt
- reservations made from another host. Not all devices support the
- ppppeeeerrrrssssiiiisssstttteeeennnntttt rrrreeeesssseeeerrrrvvvveeee oooouuuutttt command. This operation requires
- CCCCAAAAPPPP____DDDDEEEEVVVVIIIICCCCEEEE____MMMMGGGGTTTT capability.
-
- cccclllleeeeaaaarrrr
- Clears reservations. This action should only be done in error
- recovery situations. Tape support (TS) uses the clear service
- action of the SCSI ppppeeeerrrrssssiiiisssstttteeeennnntttt rrrreeeesssseeeerrrrvvvveeee iiiinnnn command to clear
- reservations made from another host. Not all devices support the
- ppppeeeerrrrssssiiiisssstttteeeennnntttt rrrreeeesssseeeerrrrvvvveeee oooouuuutttt command. This operation requires
- CCCCAAAAPPPP____DDDDEEEEVVVVIIIICCCCEEEE____MMMMGGGGTTTT capability.
-
- pppprrrrssssvvvv Shows the persistent reservation key of the device and the active
- reservation if one exists. Tape support (TS) uses the pppprrrrssssvvvv command
- on devices that support the SCSI ppppeeeerrrrssssiiiisssstttteeeennnntttt rrrreeeesssseeeerrrrvvvveeee iiiinnnn command. The
- persistent reservation key that is used by TS is the first 8 bytes
- of the hostname.
-
- hhhheeeellllpppp Print a summary of the available options.
-
-
-
-
-
- PPPPaaaaggggeeee 5555
-
-
-
-
-
-
- mmmmtttt((((1111)))) mmmmtttt((((1111))))
-
-
-
- FFFFIIIILLLLEEEESSSS
- /dev/nrtape default (no rewind) tape device
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- rmt(1M), rmtops(3), mtio(7), tps(7m).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 6666
-
-
-
-